home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93c.txt
/
000067_icon-group-sender _Tue Oct 5 10:24:55 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-02-02
|
2KB
Received: by cheltenham.cs.arizona.edu; Tue, 5 Oct 1993 09:17:11 MST
Date: Tue, 5 Oct 93 10:24:55 CDT
From: jeffery@ringer.cs.utsa.edu (Clinton L. Jeffery)
Message-Id: <9310051524.AA24738@ringer.cs.utsa.edu.sunset>
To: neil@progress.com@cs.arizona.edu
Cc: icon-group@cs.arizona.edu
In-Reply-To: (Neil Galarneau's message of 28 Sep 93 19:25:08 GMT <1993Sep28.192508.6881@progress.com>
Subject: Design for icon calling DLL entrypoints?
Content-Length: 1281
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
Hi Neil,
I think your design for .DLL access is pretty reasonable, but when you
implement it you may find a few adjustments will help. For example, it
is not easy to predefine a built-in record type in icont/iconx, and I
think its not easy to perform an Icon table lookup from within C code
in the run-time system.
I agree with you that callout() is a reasonable place to start from.
If you want to go with callout, I would stick with it entirely and
include the name of the entry point in the dll record you were talking
about, and just pass that record in as callout's first argument.
Alternatively, you could define a new function
calldll(dll, x, convention, signature, a1, ..., aN)
where x is your name or entry point, and the signature is the string encoding
argument and return types as you mentioned.
To answer your other question, I believe the Icon preprocessor is
not yet powerful enough to turn sndPlaySound("tada.wav", 0) into
callout("sndPlaySound","tada.wav", 0). Icon procedures are very
good for this sort of thing, and for the table mapping names to
records (should you decide to go with your record-based design).
It sounds like fun. Good luck!
Clint Jeffery
cjeffery@cs.arizona.edu -or- jeffery@ringer.cs.utsa.edu
The University of Texas at San Antonio